Application and platform for temporary control over property access functions

ABSTRACT

A computing device may be configured to transition control over one or more functions of a rental unit to a user (e.g., a traveler) based on one or more of time, geo-location and access credentials. Access may be granted to the traveler to use one or more home automation functions including a HVAC system, a thermostat, lighting, security alarm, automated door locks, etc. An owner of the rental unit may have access to some or all of the home automation functions blocked during the traveler&#39;s stay at the rental unit, and at an end of the stay owner access to those functions may be enabled. Some functions may be activated prior to the traveler&#39;s arrival at the unit based on a time to arrival and/or distance from the unit. An application on a traveler&#39;s computing device may be configured to summon a repair service for the unit.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is related to U.S. patent application Ser. No.14/562,629, filed on Dec. 5, 2014, having Attorney Docket No. HOM-156,and titled “Adaptive Advisory Engine And Methods To Predict PreferentialActivities Available At A Region Associated With Lodging” which ishereby incorporated by reference in its entirety for all purposes.

FIELD

The present application relates generally to systems, software,electronic messaging, mobile computing and communication devices. Morespecifically, systems, computing devices, and methods for temporarycontrol of property access and functions are disclosed.

BACKGROUND

Travelers who have booked a stay at a property, such as vacation rentalmay require access to various functions provided at the rental such askey codes for door locks, authorization for access to automated doorlocks, wireless access point network names and passwords, access toHDTV's and other electronics that may be provided, automated lightingand HVAC functions, and automated thermostats, just to name a few. Manyof the functions may be configured for wireless access via a controlsource such as a traveler's smartphone or tablet, for example.

The traveler may require an application on the traveler's smartphone ortablet to access the various functions available at the rental unit.However, the traveler may need to obtain the necessary accesscredentials, access codes (e.g., door lock codes) from the owner of therental unit. Relying on the owner to provide the correct codes in atimely manner may be problematic, especially if the owner does not liveor is unavailable in the geographic region where the rental unit islocated. It may not be possible or impracticable for the traveler tocontact the owner. Moreover, while the traveler is occupying the rentalunit, the traveler may prefer to have exclusive access to functionswithout any conflicting access to functions by the owner.

Thus, there is a need for devices, systems and methods that facilitatetemporary access and control over functions at a property for travelers.

BRIEF DESCRIPTION OF THE DRAWINGS

Various embodiments or examples (“examples”) of the present applicationare disclosed in the following detailed description and the accompanyingdrawings. The drawings are not necessarily to scale:

FIG. 1 depicts one example of temporary control over access functions ofa rental unit upon arrival of the traveler at the unit;

FIG. 2 depicts one example of a computer system;

FIG. 3 depicts one example of automated functions at the rental unitthat may be accessed by the traveler while the owner's access isblocked;

FIG. 4 depicts one example of access functions that may be activated inthe rental unit prior to the traveler's arrival based on location, time,and distance;

FIG. 5 depicts examples of an allowable location for an event;

FIG. 6 depicts an example of an application configured to present aservice request type on a display of a traveler computing device; and

FIG. 7 depicts an example of a flow diagram for transitioning access toautomated functions from an owner to a traveler;

FIG. 8 depicts one example of a flow diagram of pre-arrival functionactivation;

FIG. 9 depicts one example of a flow diagram for a service request type;

FIG. 10 depicts one example of a platform configured to performtemporary control over access functions of a property; and

FIG. 11 depicts examples of determining traveler location relative to arental unit via a traveler's computing device.

DETAILED DESCRIPTION

Various embodiments or examples may be implemented in numerous ways,including as a system, a process, a method, an apparatus, a userinterface, or a series of program instructions on a non-transitorycomputer readable medium such as a computer readable storage medium or acomputer network where the program instructions are sent over optical,electronic, or wireless communication links. In general, operations ofdisclosed processes may be performed in an arbitrary order, unlessotherwise provided in the claims.

A detailed description of one or more examples is provided below alongwith accompanying figures. The detailed description is provided inconnection with such examples, but is not limited to any particularexample. The scope is limited only by the claims and numerousalternatives, modifications, and equivalents are encompassed. Numerousspecific details are set forth in the following description in order toprovide a thorough understanding. These details are provided for thepurpose of example and the described techniques may be practicedaccording to the claims without some or all of these specific details.For clarity, technical material that is known in the technical fieldsrelated to the examples has not been described in detail to avoidunnecessarily obscuring the description.

Reference is now made to FIG. 1 where one example 100 of temporarycontrol over access functions of a rental unit 120 being transitionedfrom an owner 103 to a traveler 101 upon arrival of the traveler 101 atthe rental unit 120 is depicted. A traveler 101 may have a wirelesscomputing device 110 (e.g., a smartphone, tablet, pad, laptop, PDA,gaming device, etc.) that may be in communication with other systemsand/or resources, such as a wireless 191 and/or a wired 193communications links, an external resource 199 (e.g., Internet, Cloud,etc.), a platform 150, a wireless access point 130, a cellularcommunications network 177, a communication satellite 187 (e.g., a GPSsatellite), just to name a few. There may be more wireless computingdevices 110 and travelers 101 as denoted by 128. Wireless computingdevice 110 will be referred to as traveler device 110 hereinafter. Theremay be more or fewer wireless access points 130, cellular communicationsnetworks 177, and satellites 187 than depicted in FIG. 1 as denoted by135, 175 and 188 respectively. Data communications between the device110 and the platform 150 may be direct (e.g., via 191 and/or 193) or maybe routed through one or more other portal computing devices, such aswireless access points 130 and/or cellular communications network 140,for example. Other computing devices, such as a wireless computingdevice 113 of owner 103 (e.g., an owner of a rental property, a businessowner, etc.). Device 113 may also communicate with platform 150 usingwireless 191 and/or wired 193 communications links. There may be more orfewer devices 113 and owners 103 than depicted as denoted by 114.

Traveler device 110 and owner device 113 may transmit (119 o, 123 o)output data (119, 123) and may receive (117i, 121i) input data (117,121). Output data 119 may include location data and/or temporal datagenerated by or stored in device 110. Temporal data may be generated byan electronic system, such as a clock included in device 110. Locationdata may be generated by radio frequency (RF) systems and/or sensors indevice 110. Examples of sensors include but are not limited to one ormore motion sensors, an accelerometer, a multi-axis accelerometer, and agyroscope. Location data may be received from other communicationsresources such as from access points 130, cellular networks 177, andsatellite 187, for example. RF signals (e.g., 191) communicated betweendevices 110, 130, 177 may include location data and access points 130and cellular networks 177 may include a data store that logs orotherwise tracks location data 177L associated with one or more devices110 in geographic location 120 r. An application (e.g., APP 126) ondevice 110 may access from device 110 and/or external systems (e.g.,external resource 199, access points 130, cellular network 177, orothers), location data (e.g., GPS, geolocation or other locations basedservices) associated with device 110. Location data 177L from computingdevices (e.g., 130, 177) may be used in addition to or instead oflocation data from device 110 to determine a location of traveler 101via the traveler device 110 in the geographic location 120 r. In someexamples, location data may include information on radio frequency (RF)signals emitted by device 110, such as received signal strengthindicator (RSSI), RF signal strength, or data included in packets orother data structures included in a RF transmission 191 from device 110(e.g., MAC Address, IP address, Bluetooth address, etc.).

Wireless communications may include but is not limited to WiFi, WiMAX,Bluetooth, near filed communications (NFC), and cellular (e.g., 2G, 3G,4G), for example. Wired communications may include but is not limited tolocal area network (LAN), universal serial bus (USB), FireWire, andLightning, for example. An external resource 199 may include and/or haveaccess to computing resources 194 and data storage resources 192, andthere may be more or fewer computing resources 194 and data storageresources 192 than depicted as denoted by 197. Platform 150 may alsoinclude and/or have access to networked resources, such as computing(PROC) resources, data storage resources (DS), communications interface(COMS), and an applications programming interface (API).

In FIG. 1, APP 126 executing in association with a processor of device110 may access hardware and/or software systems and/or resources ofdevice 110 to transmit data 119 via a path 119 o to one or more externalsystems (e.g., platform 150). Data 119 may include but is not limited tolocation data, location history data, temporal data, estimated time ofarrival (ETA), distance calculation data related to events (such as anestimated arrival at rental unit 120), access credentials, mediacontent, free text, structured text, metadata, and electronic messages,for example. APP 126 may receive data 117 via a path 117 i from one ormore external systems (e.g., platform 150). Data 117 may include but isnot limited to request(s), push messages (e.g., information on otherevents for traveler 101 to consider), electronic messages (e.g., text,email, tweets, IM's), verification data (e.g., location data, accesscredential data), push location data (e.g., location data for otherevents the traveler 101 may partake in), location history, push events(e.g., events related to offers from owners 113 for the traveler 101 toconsider), applications (APP's) for traveler device 110, andconfiguration data (CFG) (e.g., to configure traveler device 110).

Further to the example of FIG. 1, the geographic location 120 r mayinclude one or more travelers 101 than depicted. Access points 130 maybe disposed at each property (120, 136) to provide data communicationsaccess with platform 150 or other resources, such as external resource199, for example. During their stay at rental unit 120, traveler 101 maymove 129 about geographic location 120 r with devices 110 and othersystems such as access points 130, cellular networks 177 and satellite187 may gather location data on device 110 as it moves 129 within region120 r.

For purposes of explanation, the following example scenario includes thetraveler 101 traveling by car 181 towards a destination at a vacationrental unit 120 located in a geographic location 120 r. A path 129depicts one example of a route that the traveler 101 may take. Alongpath 129, points 110 a-110 d depict different location along the pathwhere location data for traveler device 110 may be tracked or otherwiselogged. For example, when the traveler device 110 is far away fromaccess point 130 at the rental unit 120, longer range communicationsnetworks such as cellular networks 177 and satellite 187 may tracklocation data for traveler device 110. Different cellular networks 177may compute location data Va-Vc for traveler device and data from thoselocations may be used to determine a location of device 110 relative toa location of the rental unit 120 or some other location. For example,location data Va-Vc may be used to triangulate the location of device110 at point 110 c.

Upon arrival of the traveler 101 and his/her device at rental 120, thedevice 110 may be within a threshold Th of an allowable distance D foran allowable location (e.g., the rental 120) and within the threshold Ththe access point 130 in rental 120 may detect a radio frequencysignature of device 110 and access credentials for access to automatedfunctions available to traveler 101 at rental 120 may be activate uponverification of the access credentials. The automated functions may betransferred or otherwise transitioned from owner access (e.g., via ownerdevice 113) to traveler access (e.g., via traveler device 110) asdenoted by dashed arrow 120 a. The automated functions, as will bedescribed below in FIG. 3, may be unlocked U for the traveler 101 andowner access to those automated functions may be locked L for a periodof time, such as the duration of traveler's 101 stay at the rental(e.g., as determined by stay data 1066). Platform 150 may be configuredto lock out owner access to the automated functions upon receiving datarepresentative of the traveler's 101 access credentials being verifiedand location data consistent with the traveler's 101 presence at therental unit 120 (e.g., from location data and/or RF Signature data ondevice 110). For example, a set of codes or other data for automatedfunctions may be changed during the stay to lock-out L owner access, andupon departure of the traveler 101 from the rental 120, the codes may bechanged again to unlock U owner access to the automated functions andlock-out L traveler access to the automated functions as denoted bydashed line 120 d.

Owner 103 may own other rental units, such as an adjacent rental unit136 and the owner may still retain access to automated functions of theother rental units (e.g., rental unit 136 via owner device 113) untilsuch a time as a traveler (not shown) arrives at unit 136 to begin astay, and at that time access to the automated functions of unit 136will transfer from owner to traveler, locking-out L access for the ownerand unlocking U access for the traveler. Additional rental units thatare commonly owned by the same owner may be in the same region or may bein different regions.

The tracking of device 110 location at points 110 a-110 d or otherpoints may be used to trigger activation of one or more automatedfunctions of unit 120 prior to arrival of the traveler 101 at the rentalunit 120 as will be described below in regards to FIGS. 3 and 4. In someexample, traveler device 110 may include near field communications (NFC)capability and a near field device 120 nf in rental unit 120 may be usedto communicate with device 110 when 120 nf and 110 are placed intocontact with each other or positioned in near field proximity of eachother (e.g., 10 cm or less in distance). Near field device 120 nf may becoupled with or included in an automated function, such as a door lock,for example.

FIG. 2 illustrates an exemplary computer system 200 suitable for use inone or more systems, devices, compute engines, apparatus, travelerdevices, owner devices, wireless devices, wireless systems, backendsystems, front end systems, networked systems, platforms, data storagedevices, data storage systems, external resources, host devices orothers described in reference to FIGS. 1, 3-6 and 10-11. In someexamples, computer system 200 may be used to implement computerprograms, algorithms, an application (APP), an application programminginterface (API), configurations, methods, processes, or other softwareto perform the above-described techniques. Computer system 200 mayinclude circuitry, hardware, and other electronic systems to perform theabove-described techniques. Computer system 200 may include a bus 202 orother communication mechanism for communicating information, whichinterconnects subsystems and devices, such as one or more processors 204(e.g., μC, μP, DSP, ASIC, FPGA, Baseband, etc.), system memory 206(e.g., RAM, SRAM, DRAM, Flash), storage device 208 (e.g., Flash, ROM),disk drive 210 (e.g., magnetic, optical, solid state), communicationinterface 212 (e.g., modem, Ethernet, WiFi, Cellular), display 214(e.g., CRT, LCD, LED, OLED, touch screen), input device 216 (e.g.,keyboard, stylus, touch screen, mouse, track pad), and cursor control218 (e.g., mouse, trackball, stylus). Some of the elements depicted incomputer system 200 may be optional, such as elements 214-218, and oneor more clocks 240 which may provide temporal data, for example, one ormore sensors 230 which may provide location data, rate of motion dataand other data associated with movement 129, and computer system 200need not include all of the elements depicted. Display 214 may present auser interface (UI), such as a graphical user interface (GUI) 214 a.

Memory 206 may include computer executable programs and/or data embodiedin a non-transitory computer readable medium, such as an operatingsystem (OS) 206 a, an application (APP) 206 b, and executable code(Ex-Code) 206 c, for example. APP 206 b may be an application that maybe downloaded or otherwise installed from a location such as anapplication store (e.g., Google Play® or the App Store®), for example.

According to some examples, computer system 200 performs specificoperations by one or more processors 204 executing one or more sequencesof one or more instructions stored in system memory 206. Suchinstructions may be read into system memory 206 from anothernon-transitory computer readable medium, such as storage device 208 ordisk drive 210 (e.g., a HDD or SSD). In some examples, circuitry may beused in place of or in combination with software instructions forimplementation. The term “non-transitory computer readable medium”refers to any tangible medium that participates in providinginstructions and/or data to processor(s) 204 for execution. Such amedium may take many forms, including but not limited to, non-volatilemedia and volatile media. Non-volatile media includes, for example,optical, magnetic, or solid state disks, such as disk drive 210.Volatile media includes dynamic memory, such as system memory 206.Common forms of non-transitory computer readable media includes, forexample, floppy disk, flexible disk, hard disk, SSD, magnetic tape, anyother magnetic medium, CD-ROM, DVD-ROM, Blu-Ray ROM, USB thumb drive, SDCard, any other optical medium, punch cards, paper tape, any otherphysical medium with patterns of holes, RAM, PROM, EPROM, FLASH-EPROM,any other memory chip or cartridge, or any other medium from which acomputer may read.

Sensor(s) 230 may include but are not limited to one or more inertialsensors (e.g., an accelerometer, a multi-axis accelerometer, agyroscope, a magnetometer, etc.), an altimeter, and a barometer, forexample. One or more sensors in sensor(s) 230 may be used to determinelocation data for a device that includes computer system 200 and/or isin communication with computer system 200 (e.g., a client device, asmartphone, a tablet, a pad, a laptop, PC, a wireless device, a portalcomputing device, a computing device, a networked computing device, aplatform, a backend service, etc.). One or more of the memory 206,storage device 208, or disk drive 210 may be accessed as a data storefor location data from sensor(s) 230 or other systems in communication(e.g., via communications interface 212) the computer system 200.Location data may be communicated to/from the computer system 200 viaone or more of the wireless transceivers 213.

For example, radio frequency signal sources including but not limited toGPS satellite signals (e.g., signals 191 from one or more GPS satellites187), terrestrial location transmitters (e.g., one or more cellulartowers), WiFi signals, WiMAX signals, WiFi routers, WiFi access points,Bluetooth signals (e.g., Bluetooth beacons), near field communicationsignals, iBeacons, data from external resource 199, and platform 150.Other signal and/or data sources for location data may include but arenot limited to audio signals (e.g., ultrasonic signals) and signalsand/or data generated by location tracking software (e.g., internal toand/or external to computer system 200), for example. In some examples,location data and/or signals may be communicated wireless communicationslink (e.g., 191) and/or a wired communications link (e.g., 193).Location data accessed by computer system 200 may include but is notlimited to a location history data base (e.g., 147) and location data1030, for example. The location data may be updated, revised orotherwise change on a dynamic basis as the guest device 110 moves 129around in areas around event 120.

Instructions may further be transmitted or received using a transmissionmedium. The term “transmission medium” may include any tangible orintangible medium that is capable of storing, encoding or carryinginstructions for execution by the machine, and includes digital oranalog communications signals or other intangible medium to facilitatecommunication of such instructions. Transmission media may includecoaxial cables, copper wire, and fiber optics, including wires thatcomprise bus 202 for transmitting a computer data signal or othersignals (e.g., from hardware or circuitry). In some examples, executionof the sequences of instructions may be performed by a single computersystem 200. According to some examples, two or more computer systems 200coupled by communication link 220 (e.g., LAN, Ethernet, PSTN, USB, orwireless network) may perform the sequence of instructions incoordination with one another. Computer system 200 may transmit andreceive messages, data, and instructions, including programs, (i.e.,application code), through communication link 220 and communicationinterface 212. Received program code may be executed by processor 204 asit is received, and/or stored in disk drive 210, or other non-volatilestorage for later execution. Computer system 200 may optionally includea wireless transceiver 213 coupled with the communication interface 212and coupled 215 with an antenna 217 for receiving and generating RFsignals (191, 221), such as from a WiFi network, WiMAX network, BTradio, Cellular network, networked computing resources, externalresource 199, client devices (e.g., 110), owner devices (e.g., 113),near field communication (NFC), satellite network, data storage network,or other wireless network and/or wireless devices, for example. Examplesof wireless devices (e.g., client devices) may include but is notlimited to those depicted in FIGS. 1, 3-6 and 10-11. Communicationsinterface 212 may be coupled 222 with data storage external to computersystem 200. Communications interface 212 may be coupled 193 withexternal resources and/or systems, such as those depicted in FIGS. 1,3-6 and 10-11, for example. Computer system 200 may be used to implementa computing device (e.g., 110, 113), a portal computing device (e.g.,130, 177, 180), a networked computing device (e.g., 1053, 1055, 1059,1080), the platform 150, and external resource (e.g., 199), for example.

Processor(s) 204 may be coupled 202 with signals from circuity or otherhardware systems of computer system 200. For examples, signals fromclock 240, sensors 230, and communications interface (e.g., via wirelesstransceivers 213) may be processed by processor 204 and/or othercircuitry to calculate an estimated time of arrival of the device 110(e.g., due to motion 129 of traveler 101 carrying device 110) at anevent in geographic location 120 r. The ETA may be calculated based ontime data from clock 240 and one or more of location data, speed data(e.g., scalar data), or velocity data (e.g., vector data). Speed orvelocity data may be calculated from signals from sensors 230 andchanges in location data as traveler 101 and his/her associated device110 move 129 relative an some event or other reference point. Rate oftravel (e.g., distance traveled per unit of time) may be calculatedusing signals from clock 240, sensors 230 and/or location data.

Moving on to FIG. 3 where one example 300 of automated functions at therental unit 120 that may be accessed by the traveler while the owner'saccess is blocked are depicted. Non-limiting examples 301 and 302 ofautomated functions that may be made available for access by thetraveler 101 in rental unit 120 may include but are not limited to door310 access via wireless 191 communication with traveler device 110 orother wireless device or using a keypad 321 to enter an access codeprovided by the platform 150 upon verification of access credentials, anautomated thermostat 312 which may be coupled with a HVAC system 340 andmay include external sensor 312 s for obtaining outdoor ambientconditions such a temperature, humidity, barometric pressure, wind speedand direction, a garage door 314 that may be open/closed via wireless191 communications, a HDTV 316 for which access codes for remotecontrols or cable/pay content may be provided, a security system 318which may be wirelessly 191 controlled and/or by provided security codes319, automated lighting systems 320, security cameras 322, a gate 324 toa pool or other amenity, a washing machine 326 and dryer 328, HVACsystem 340 including a heater 332 and AC unit 334, and a hot tub 330,just to name a few. The automated functions may be wirelessly enabled asdenoted by 191 and/or may be enabled for wired 193 communication (notshown). Some automated functions may be interrelated such as securitycameras 322 with security system 318 or hot tub 330 with automatedthermostat 312, for example.

Transfer of automated functions to traveler 101 may include providingaccess to wireless access point 130 by providing wireless network keyand SSID information needed to access 130. In FIG. 3, while traveler 101is in possession of rental 120, owner 103 is locked-out L from accessand traveler 101 has unlocked U access to the automated functions. Insome examples, traveler device 110 may control access to the automatedfunctions via wireless 191 link with the functions or via access point130. While traveler device is within an allowable distance D from accesspoint 130 as denoted by reference point E0, access may be unlocked U;however, if traveler device 110 moves to a point Dx that is outside theallowable distance, access may be locked L until the traveler device 110moves back into a range inside the allowable distance D. Access codes,credential, and other information used to access the automated functionsfor rental unit 120 may be different for travelers 101 than for owner103 and may be changed for each traveler 101 that rents unit 120. InFIG. 3, platform 150 may communicate via wireless 391 and/or wired 393communications links with access point 130 or other types of portalcomputing devices, such as a bridge, to communicate (e.g., via accesspoint 130) with devices having automated functions and/or with travelerdevice 110 to control or otherwise activate devices having automatedfunctions and/or enable access (e.g., to lock L or unlock U) to traveler101 via traveler device 110.

Turning now to FIG. 4 where one example 400 of access functions that maybe activated in the rental unit 120 prior to the traveler's 101 arrivalat the rental unit 120, based on location, time, and distance or otherfactors are depicted. In FIG. 4, prior to traveler's 101 actual arrival440 a at the rental 120, the traveler 101 and his/her device 110 maytravel a path 429 in car 181 in route to rental unit 120. Locations ofthe traveler device 110 along the path 429 are denoted as Loc-a-Loc-d.Each of those locations may also represent a distance from rental 120.Depending on the speed or velocity of car 181, an estimated time ofarrival at the rental 120 or to one or more of the locations Loc-a-Loc-dwill vary with the speed or velocity. Traveler data 1061 about traveler101 or owner 103 information about traveler 101 may be used to determinewhich automated functions of rental 120 to activate (e.g., to turn on)prior to the traveler's 101 actual arrival 440 a at the rental 120.

For example, at a time before actual arrival 440 a, the owner may desireto have one or more of the automated lights 320 be activated (e.g., turnthe lights 320 on) prior to arrival if the traveler 101 will be arrivingat night time. For example, at an approximate estimated time of arrivalof the traveler device 110 at location Loc-d denoted as ETA-d, a signalmay be wirelessly communicated to trigger activation 420 a of thelighting function to turn lights 320 on (e.g., interior and/or exteriorlights 320). Due to changes in speed and/or route 429 taken, ETA-d maychange (e.g., +/−Δt0 in FIG. 11). Therefore, platform 150 may adjust theETA-d based on location data, changes in speed and/or direction oftraveler device 110 so that the lights 320 aren't activated long beforethe traveler is near the rental 120, thereby preventing wasted energyconsumption.

As another example, depending on the time of year, temperature, weatherconditions, etc., the HVAC system 340 may be activated 440 a prior toactual arrival 440 a of the traveler 101, to heat or cool the rentalunit 120. An estimated time ETA-c to a location Loc-c may be computed toactivate the HVAC system 340 at a sufficient time before arrival 440 aof traveler 101 so that a temperature of the rental 120 has had time toreach an appropriate set point, such as 68 degrees Fahrenheit for ACunit 334 when cooling is called for or 75 degrees Fahrenheit for Heaterunit 332 when heating is called for.

As another example, hot tub 330 may be activated 430 a at an ETA-b thatallows sufficient time for the water in hot tub 330 to be heated orcooled to a desired temperature based on the exterior ambientconditions, which may be sensed by sensor 312 s.

Location data 147, 177L, 1030 may be accessed by platform 150 and/ordevice 110 to modify ETA's to locations Loc-b-Loc-d as necessary so asto trigger activation 420 a, 430 a, 440 a at a time that is not tooearly or too late to conserve energy or other resources, for example.Platform 150 may communicate via wired 393 and/or wireless 391communications links with a portal computing device (e.g., access point130) to trigger activation of one or more of the units 320, 330 and 340.Commands, signals, data or other information communicated by platform150 may be received by access point 130 and communicated (191 and/193)to a control unit CNTL 490 in units 320-340, the control unit 490configured to activate functions of units 320-340 and to communicatestatus data (e.g., unit is ON, unit is OFF, unit in standby mode, etc.),maintenance data (e.g., unit requires maintenance or repair), or otherinformation with platform 150 and/or traveler device 110, for example.

Attention is now directed to FIG. 5 where examples 500 and 550 of anallowable location of an event (e.g., rental 120) are depicted. Inexample 500 the event 120 is a stay at a vacation rental unit 120 whereguest 101 and his/her client device 110 are present. WiFi access point130 (e.g., a portal computing device) is positioned in the rental unit120 and includes access credentials 130 c. Concentric circles 501 depicta radial distance 130 d centered about access point 130 where athreshold for an allowable distance denoted as a black dot “” fordevice 110, for an allowable location (e.g., event 120) may be used by anetworked computing device (e.g., 153, 155, 159) to determine locationdata as described in reference to FIGS. 1, 3-4, 6 and 10-11, forexample. For purposes of explanation a distance 503 between adjacentcircles in 501 may be 3 meters, for example. Distances that are not anallowable distance are denoted by a “×” 510 and some of those distancesmay fall outside of circle 501.

For example, as a distance of the traveler device 110 increases alongdirection of the arrow for radial distance 130 r, locations associatedwith “×” 510 may increase; whereas, as a distance of the traveler device110 increases along direction of the arrow for radial distance 130 r,locations associated with “” 110 may increase.

In example 550, as the traveler device 110 moves closer to or furtheraway from access point 130 as denoted by dashed line 551, a RF signalparameter may change as a function of distance along 130 d. As anexample, RSSI or RF signal strength associated with 1-bar 510 a or2-bars 510 b for “×” 510 may be indicative of the client device 110being outside the allowable distance. On the other hand, at closerdistances to access point 130, RSSI or RF signal strength associatedwith 3-bars 110 x or 4-bars 110 y for “” 110 may be indicative of thetraveler device 110 being inside the allowable distance. Hardware,software, circuitry, RF systems or the like in access point 130 mayinclude signal strength data indicative of a relatively strong signal(e.g., 4 to 5 bars), an adequate signal (e.g., 3 bars), or a relativelyweak signal (e.g., one to two bars) in data 119. The signal strengthdata may be used by the platform 150 to determine location data. APP 126may access systems of traveler device 110 (e.g., RF system) and includesignal strength data in the data 119 and the signal strength data may bemay be used by the platform 150 to determine location data. Access toautomated functions of rental 120 may be blocked L for signal strengthof 1 to 2-bars and unblocked for signal strength of 3 to 4-bars, forexample.

Further to example 500, owner 103 may own 545 both rental units depicted(e.g., 120 and 540). An access point 530 with access credentials 530 cin rental unit 540 may be detected by and may even be accessed bytraveler device 110 of traveler 101. For example, another guest in 540may give the access credentials for access point 530 to traveler 101.However, data 119 transmitted by traveler device 110 using access point530 may not be authenticated due to the credential data in 119 notmatching the access credentials assigned to rental 120. Use by traveler101 of access point 530 to communicate data 119 to/from platform 150 mayresult in credential data not being authenticated and datacommunications access being denied. Other communications resourcesand/or portal computing devices may be used to determine location, suchas cellular networks 177, other wireless access points 130 and theassociated location data 177L generated by those devices. As oneexample, two or more cellular networks 177 may be used to locatetraveler device 110 in location 120 r using triangulation or otherlocation techniques. Access points 130 positioned near or at events maybe used to sense signals from traveler device 110 and determine arelative location of the traveler device 110.

Referring now to FIG. 6 where an example 600 of an applicationconfigured to present a service request type 610 on a display 111 of atraveler computing device 110 is depicted. Now in FIG. 6, traveler 101may encounter a maintenance issue in rental 120, such as amalfunctioning washer 326 or dryer 328, or a leaky faucet 611, forexample. An application (e.g., APP 126) on traveler device 110 maypresent on a display 111 (e.g., a touch screen) of the device 110 anicon, image, graphic, or other user interface information that may beselectable 601 (e.g., by a finger of a hand 101h of traveler 101). Amaintenance issue may be communicated 191 wirelessly to traveler device110 and/or platform 150 by control unit 490 and data representing aservice request type (e.g., plumbing, HVAC, electrical, etc.) needed bythe malfunctioning unit (e.g., 326 or 328) may be presented on thedisplay 111. In some examples, the maintenance issue may not be one thathas a dedicated icon, and a generic icon, such as 610 may be presented.Traveler 101 may use a GUI keyboard of device 110 to enter text and/ormenu selections to describe the maintenance issue.

In example 620, activation 601 of the icon 610 may cause APP 126 tocommunicate a service call 626 to a service provider 625 for the servicerequest type needed, which for purposes of explanation will be the leakyfaucet 611. Accordingly, service provider 625 skilled in plumbing issuesmay be dispatched 628 to unit 120 to repair the leaky faucet 611. Astatus message 629 may be communicated to device 110 to notify thetraveler 101 when the service provider 625 will arrive at the unit(e.g., in case the traveler does not wish to be in unit 120 duringrepairs). Status message 629 may include an estimated repair time. Thestatus message 629 may inform traveler when repairs are completed and/orapprise the traveler 101 that the service provider 625 has vacated therental unit 120. The status message 629 may include other informationand the foregoing are non-limiting examples.

In example 630, activation 601 of icon 610 may cause APP 126 tocommunicate a service call 631 to a third party 635. The traveler maynot be aware that the service call is being communicated to a party thatis not the service provider for the service request type needed. In someexamples, the third party 635 may be the platform 150. In otherexamples, the third party 635 may be the owner 103. In yet otherexamples, the third party may be a warranty company 636 (e.g., undercontract to the owner 103 or a property management company that overseesrental 120). The communication to the third party 635 may be transparentto traveler 101 and third party 635 may contact 633 a service provider639 who is subsequently dispatched 638 to rental unit 120 to effectuaterepairs. As described above, traveler device 110 may receive a statusmessage 637. In the case where the third party 635 is the owner 103, theAPP 126 may be configured to contact owner 103 in order for owner 103 toselect a preferred service provider based on cost, location of therental unit 120, type of repair needed, etc. Service provider (625, 639)may be granted limited access to automated functions of rental 120(e.g., by signals from a computing device of the service provider thatis positioned within the threshold Th).

Turning now to FIG. 7 where an example of a flow diagram 700 fortransitioning access to automated functions from an owner to a traveleris depicted. Platform 150 may perform one or more of the stages depictedin FIG. 7 using one or more hardware and/or software systems and/orfunctions. At a stage 702 data representing access credentials for anautomated function of a rental unit (e.g., one or more automatedfunctions of unit 120) may be received. For example, communicationsinterface 1080 of FIG. 10 may receive the data.

At a stage 704 data representing stay data for a stay at the renal unitmay be accessed (e.g., from stay data 1066). At a stage 706 the datarepresenting the access credentials may be verified (e.g., by comparingwith data accessed from credential data 1064). At a stage 708, after thedata representing the access credentials has been verified, access tothe automated function may transition from owner access to traveleraccess. (e.g., owner 103 is locked-out L of access and traveler 101 hasunlocked U access to the automated function(s)).

At a stage 710 owner access to the automated function may be blocked(e.g., credentials changed, codes changed, etc.) during the stay oftraveler 101. At a stage 712, on occurrence of an event, such as thetraveler 101 departing the rental at the end of the stay (e.g.,check-out time) or an emergency at the rental 120, access to theautomated function may re-transition back to owner access from traveleraccess (e.g., credentials changed, codes changed, etc.). At a stage 714,owner access to the automated function may be un-blocked and traveleraccess to the automated function may be blocked.

Moving to FIG. 8 where one example of a flow diagram 800 of pre-arrivalfunction activation is depicted. Platform 150 may perform one or more ofthe stages depicted in FIG. 8 using one or more hardware and/or softwaresystems and/or functions. At a stage 802 data representing location datafor a location of a traveler computing device (e.g., 110) may beaccessed (e.g., location data 1030, 177L, 147). At a stage 804 datarepresenting pre-arrival activation data of an automated function of arental unit (e.g., 120) may be received. At a stage 806 datarepresenting a function activation time extracted from the pre-arrivalactivation data may be received. At a stage 808 data representing anestimated time of arrival (ETA) of the traveler computing device at therental unit (e.g. 120) may be received. At a stage 810 an estimatedlocation of the traveler computing device at the function activationtime may be calculated (e.g., by 110). At a stage 812 a match betweenthe function activation time and a time the traveler computing devicereaches the estimated location may be determined. At a stage 814 theautomated function may be activated (e.g., turned ON) if the match isdetermined.

Attention is now directed to FIG. 9 where one example of a flow diagram900 for a service request type is depicted. At a stage 902 informationrepresenting a service type request (e.g., icon 610) at a rental unitmay be presented on a display (e.g., 111) of a traveler computing device(e.g., 110). At a stage 904 data representing a selection of the servicerequest type may be communicated by a communications interface of thetraveler computing device. At a stage 906 data representing a servicetype request may be received at a computing device (e.g., 113 and/or150). At a stage 908 data representing the service type request may beextracted from the data received. At a stage 910 a type of serviceneeded at the rental unit (e.g., 120) may be determined based on theservice request type (e.g., plumbing, electrical, appliance, etc.). At astage 912 data representing the selection of the service request type iscommunicated (e.g., 628, 633) to a service provider (e.g., 625, 639)using the communications interface of the traveler computing device. Ata stage 914 data representing a service status (e.g., 629, 637) iscommunicated to the traveler computing device.

Reference is now made to FIG. 10 where one example of a platform 150configured to perform temporary control over access functions of aproperty is depicted. Platform 150 may be a platform that includes acommunications interface and data storage and processing resources incommunication with the communications interface using wired 193 and/orwireless 191 communications links. Platform 150 may be in wired 193and/or wireless 191 communications with other devices and systems,including but not limited to external resource 199 and its associatedresources (192, 194), traveler device 110, owner device 113, and othercomputing devices, just to name a few. Platform 150 may includeresources in communications with one another, that may include but isnot limited to an application program interface (API) 1041, executablecode 1042, one or more laptop computers 1059, one or more servers 1053,a communications interface 1080 that may include wireless 191 (e.g., awireless 1081 access point), and wired 193 links, firewall 1057, one ormore server farms 1055, data storage 1060, location data 1030 which mayinclude location history data from traveler device 110 (e.g., a locationhistory data base), event data 1065 (e.g., for events in region 120 rwhich may include the rental unit), credential data 1064 (e.g., WiFiaccess point network name and SSID for access point 130, key codes, andother access credentials), owner data 1063 (e.g., owner contactinformation, emergency contact information, rental unit policies, etc.),traveler data 1061 (e.g., traveler preferences, information on travelerdevice(s) 110, contact information, email address, addresses for otherelectronic media/accounts, etc.), stay data 1066 (e.g., beginning/endingdates and/or times for a stay, rental location, rental automatedfunctions, rental amenities, etc.), rental unit data 1020 (e.g.,amenities, geographic location, wireless access point 130 information,rules, polices, automated equipment/functions, etc.), and electronicmessages 1070. In some examples, data storage 1060 may include one ormore of the other above described data storage categories. In otherexamples, data storage resources accessed by platform 150 may beexternal to platform 150 (e.g., positioned in external resource 199).One or more of the flows depicted in FIGS. 7-9 may be implemented usinghardware, circuitry, executable code 1042 and/or API 1041, for example.For purposes of explanation, a computing resource (e.g., 1053, 1055,1059) depicted in FIG. 10 may be referred to as a networked computingdevice and a data storage resources may be referred to as data storageor a data store. For example, data 119 may be received by networkedcomputing resource 1053 via communications interface 1080. In someexamples, a computing device that transmitted the data 119 may bereferred to as a traveler device (e.g., 110) or a portal computingdevice (e.g., 130, 177). As another example, data 123 from owner device113 may be received by networked computing resource 1053 viacommunications interface 1080 and the data 123 may include credentialdata for the owner device 113, that once verified, allows datacommunications access to platform 150.

Traveler device 110 and/or owner device 113 may communicate (191, 193)with platform 150 via a Web Site/Web Page 1080 (e.g., using a browser orapplication on a laptop, PC, wireless device, smartphone, pad, tablet,touch screen device, etc.). Information (117, 119, 121, 123) may beviewed, entered, transmitted, received, or otherwise communicated (191,193) between platform 150 and another device (e.g., 110, 113, etc.)using Web Site/Page 1080. Data associated with rental unit 120 or otherevents in region 120 r may be communicated via Web Site/Page 1080.Platform 150 may require access be granted to a device (e.g., 110, 113,etc.) prior to allowing data communication with the platform 150 via WebSite/Page 1080. Traveler device 110 may include a biometric sensor(e.g., see fingerprint scanner 118 in FIG. 6) to verify accesscredentials for data communications between platform 150 and travelerdevice 110, for example and/or between platform 150 and owner device113, for example.

Location data 1030 may include locations (e.g., GPS data and/or otherlocation data) associated with events (e.g., rental unit 120, events in120 r) and locations around events (e.g., in approximately the samelocale as an event). Examples of location around an event may includebut are not limited to a park across the street from an event, a cafe ofcoffee shop down the street from an event, etc. Examples of ownerlocations may include location data associated with use of the ownerdevice 113, such as location data from cellular networks (e.g., in thecity or state the owner or a rental property or other types of eventslives in), WiFi networks, WiMAX networks, etc.

Event data 1065 may include data for the stay at rental unit 120, anentertainment venue, a bar, a grocery store, a bakery, goods, services,business, restaurants, etc. that may be the primary event for traveler101 or may be associated with activities the traveler 101 partakes induring his/her stay at the primary event (e.g., the stay at the rental120).

Location data 1030 may include a location history data base. Thelocation history data base may include location data tracked and storedover time based on various locations visited by traveler 101 withtraveler device 110 that includes or has access to internal/externalsources of location data, such as satellite 187, access points 130,cellular networks 177, etc. Validation of location of a traveler 101 mayinclude accessing data in location data 1030, the location history database included in 1030, or both. In some examples, a computing devicethat communicates the data 119 (e.g., device 110) may include locationhistory data base (e.g., 147) which may include the same or differentdata than the location history data base in 1030. In some exampleslocation data in one of the location history data bases may be used toupdate and/or replace location data in another location history database.

Credential data 164 (e.g., access credentials, user name, password,etc.) may be a data store where access data is retained for variousevents, owner properties, etc. For example, credential data 164 mayinclude credentials for WiFi access points (e.g., 130) in a rental unit,in owner properties (e.g., 120, 136), businesses that may be promoted bythe owner 103 or by an agent acting on behalf of the owner, etc. Otherforms of credentials may be included in credential data 164, such asaccess credentials for traveler devices (e.g., 110), locks on doorsneeded to gain access to a rental property or other protected areaassociated with a stay at an event (e.g., event 120), for example.

Electronic messages 1070 may be a data store for incoming and/oroutgoing electronic messages, such as emails, push notifications, pushevents, and electronic messages generated by one or more of platform150, owner 103, or traveler 101, for example. Electronic messages 1070may include data in 117, 121, 119 and 123, for example. Electronicmessages 1070 may be presented on a display of device 110, 113, or website/page 195, for example.

Rental unit data 1020 may include information on a rental unit (e.g.,event 120, 136) that may be accessed by traveler 101, such as amenities,rental policies (e.g., no smoking, no pets), parkinginstructions/locations/restrictions, maps, address information,electronic devices in the rental unit, appliances, maintenance contactinformation, owner information, emergency information, policies for useof facilities (e.g., swimming pools, workout room, club house, etc.),just to name a few.

Owner data 1063 may include data about owners (e.g., 103), such asproperty addresses, owner address and contact information, emailaccounts, account information for a vacation rental agency the owneruses to manage stays by guests, travelers, users, data on owner devices113 (e.g., MAC address or other forms of device ID, etc.).

Traveler data 1061 may include data about travelers (e.g., 101), such asaddresses and contact information, email accounts, travelerdemographics, data on traveler devices 110 (e.g., MAC address or otherforms of device ID, etc.), financial accounts for deposits, payments,refunds, etc.

Stay data 1066 may include data for an event such as stay dates,check-in/check-out times/dates, event address, maps to events,directions to events, event categories for different types of events(e.g., vacation rental events, restaurant events, casino events, etc.).Verification of access credentials for a traveler, transitioning ofautomated functions from owner access to traveler access or both, to arental unit (e.g., rental unit 120) may be conditioned on an eventrepresented by data included in the stay data, such ascheck-in/check-out times/dates, for example. As one example, presentingcorrect access credentials prior to a check-in time/date included in thestay data may block traveler access to automated functions because thetravelers stay at the rental unit has not yet begun.

Data storage 1060 may be used as a data store that may be accessed byother components internal to and/or external to platform 150. Platform150 may include more or fewer resources than depicted in FIG. 10 asdenoted by 1052.

Platform 150 may share data processing and/or data storage with externaldevices, such as traveler devices 110, owner devices 113, externalresource 199, for example. As one example, hardware systems (e.g., seeFIGS. 2 and 11) circuitry, sensors 230, clock 240) of traveler device110 may perform calculations, signal processing or other electronicfunctions and communicate data (e.g., via 119) to platform 150. Forexample, location data resources of device 110 in conjunction withcircuitry that receives signals from sensors 230 and/or clock 240 may beused to determine a rate of speed and direction (e.g., velocity) oftraveler device 110, and data from that determination may becommunicated (e.g., via 191 and 119) to platform 150. The data may beused to calculate whether or not a traveler 101 is heading toward andevent in 120 r or away from and event in 120 r. The data may be used todetermine if the traveler 101 will arrive at an event in 120 r within aspecified time window set for the event or will enter into the thresholddistance (e.g., Th) for the event (e.g., a stay at rental unit 120)within a specified time window based on a velocity of the traveler 101(e.g., as sensed by motion of traveler device 110).

Attention is now directed to FIG. 11 where an example 1100 of trackingtemporal and location data for a traveler device 110 and an example of ablock diagram 1120 for an estimator are depicted. In example 1100 anevent 120 (e.g., a rental unit) has a threshold Th for an allowabledistance for an allowable location for the event 120. For purposes ofexplanation, threshold Th may define as circle 1101 centered about event120 such that the traveler device 110 being on or in the circle 1101positions the traveler 101 within the threshold Th for the event 120.Dashed line 1105 represents a distance of the traveler device 110 fromthe event 120 and that distance may change as the traveler device 110moves in a direction away from the event 120 as denoted by R+ (e.g.,distance is receding) or traveler device 110 moves in a directiontowards the event 120 as denoted by C− (e.g., distance is closing). Asone example, if distance between the traveler device 110 and the event120 is closing C−, then traveler 101 may be moving 129 in the geographiclocation 120 r for the event 120 in a direction towards the event 120 asdenoted by 101 t moving from the left of the drawing sheet to beinginside the circle 601. As another example, if the distance between thetraveler device 110 and the event 120 is receding R+, then traveler 101may be moving 129 in the geographic location 120 for the event Et in adirection away from the event 120 as denoted line by 101 t movingfurther to the left of the drawing sheet on line 607.

Location data from traveler device 110 and/or from sources external totraveler device 110 may be accessed to calculate the approximatedistance between the traveler device 110 and the event 120, the rate ofclosure C− if the traveler device 110 is moving towards the event 120,the rate of recession R+ if the traveler device is moving away from theevent 120, for example. Temporal data from the traveler device 110(e.g., from a clock or oscillator in device 110) and/or an externalsource (e.g., 150, 130, 177) may be used in determining speed of closureC+ or speed of recession R− and/or a velocity of traveler device 110(e.g., speed and direction) relative to the event 120 (e.g., a velocityvector V).

The temporal data and location data may be used to determine anestimated time of arrival of the traveler 101 at the event 120. Forexample, a time t0 may be a time associated with the event 120, such asa check-in time of 3:00 pm. Time windows −Δt0 and +Δt0 may representtimes prior to time t0 (e.g. where −Δt0 may mean arriving early) orafter (e.g., where +Δt0 may mean arriving late) where the traveler 101is estimated to arrive within the threshold Th. In some examples, theremay be some tolerance to the deltas +/−Δt0 for the arrival times.Location tracking data (e.g., from terrestrial sources 177 and/ororbital sources 187) may be used to determine device 110 speed and/ordirection and temporal data may be used to determine an estimated timeof arrival (ETA) at the event 120 (e.g., at a time t0 or a time relativeto t0 as +/−Δt0). In some examples, event 120 may be in data received(e.g., 117) by device 110 and device 110 may use internal resources(e.g., clock 240, sensors 230, circuitry, location data, locationhistory data) to calculate speed, velocity, ETA and other parametersassociated with moving towards C− or away R+ the event 120.

In example 1100, the traveler 101 may not have notification of the or beable to take action on access functions for event 120 until the travelerdevice 110 is within some predetermined distance around the event 120 asdenoted by dashed line 1103. Platform 150 may track device 110 and upondetermining the device 110 is at least within the predetermined distance1103, initiate data communications with device 110 for purposes oftemporary control over access functions for rental unit 120 and/orpre-arrival activation of one or more functions in the rental unit asdescribed in reference to FIG. 4. Threshold Th may be 50 meters or less,and predetermined distance 1103 may be a larger distance, such as one ormore kilometers, for example.

As estimated arrival time at rental unit 120 changes (e.g., due totraffic, detours, sightseeing, etc.) activation of automated events maystill occur at a time relative to the time t0, such as traveler 101arriving at 120 early as denoted by −Δt0 or traveler arriving late +Δt0.For example, in FIG. 4, if the pre-arrival function to be activatedbefore the traveler 101 arrives at rental unit 120 is turning on lights320, if the traveler 101 is arriving early, then the lights 320 may beturned on before time t0 somewhere in the −Δt0 window; whereas, if thetraveler 101 is arriving late, then the lights 320 may be turned onafter time t0 somewhere in the +Δt0 window. Although line 1105 isdepicted as being a straight line, the path take to event 120 need notbe straight or linear and may be arcuate and/or circuitous with manybends, curves, etc. The +/−Δt0 may be applied to other times such asthose depicted in FIG. 4, such that ETA-a-ETA-d may have +/−Δt timesassociated with them based on traveler device 110 changes inspeed/velocity and location. As one example, hot tub 330 may beactivated at time t0 if traveler 101 arrives about at the 3 pm check-intime. However, the hot tub 330 may be activated earlier (−Δt0 window) ifthe traveler 101 arrives to the rental 120 earlier than scheduled, ormay be activated later (+Δt0 window) if the traveler 101 arrives to therental 120 later than scheduled. Location data (1132, 1134) may betracked or otherwise updated or refreshed in real-time or near real-timeto track progress of traveler 101 and his/her device 110 towards or awayfrom the rental 120 or some other event in region 120 r.

In block diagram 1120 an estimator 1140 is coupled with mobile devicelocation data 1132, data and/or signals from one or more clocks 1122,stay data 1124 (e.g., from stay data 1066), target location 1125 (e.g.,geographical location of rental unit 120 from rental unit data 1020,stay data 1066, event data 1065, etc.), external location data 1134(e.g., from 117, 187, etc.), and temporal data 1127 (e.g., from staydata 1066, event data 1065).

Estimator 1140 may include an estimated time of arrival (ETA) calculator1142 (e.g., circuitry, software or both for estimating time of arrivalbased on input to Estimator 1140). Location data from 1132, 1134 or bothmay be used to determine a current location of traveler device 110relative to the target location data 1125. Estimator 1140 may alsoinclude a distance estimator 1144. Distance estimator 1144 and ETAestimator 1142 may be electrically coupled 1141 and may transmit and/orreceive signals and/or data between each other operative to calculateETA or estimated distance. Distance estimator 1144 may take as inputs acurrent location of traveler device 110 (e.g., from 1132, 1134) relativeto the target location data 1125 (e.g., for event 120) and estimate adistance between the traveler device 110 and the target location.Distance estimator 1144 may calculate a rate of change in location data(e.g., from 1132, 1134) to determine a speed (scalar) or velocity(vector) for the traveler device 110 (e.g., as traveler 101 moves 129through region 120 r by car 181, etc.). ETA estimator may use thevelocity and/or speed to determine the ETA to the target location or toone or more other locations such as locations Loc-a-Loc-d in route tolocation 120 as depicted in FIG. 4.

Although the foregoing examples have been described in some detail forpurposes of clarity of understanding, the above-described conceptualtechniques are not limited to the details provided. There are manyalternative ways of implementing the above-described conceptualtechniques. The disclosed examples are illustrative and not restrictive.

What is claimed is:
 1. A method, comprising: receiving data representingaccess credentials for access to an automated function of a rental unit;accessing data representing stay data for the rental unit; verifying thedata representing the access credentials; transitioning, after the datarepresenting the access credentials have been verified, access to theautomated function from owner access to traveler access; blocking owneraccess to the automated function of the rental unit after thetransitioning; re-transitioning, on occurrence of an event, access tothe automated function of the rental unit from traveler access to owneraccess.
 2. The method of claim 1, wherein the event comprises datarepresenting a check-out time, a check-out day or both extracted fromthe stay data.
 3. The method of claim 1, wherein the event comprisesdata representing an emergency at the rental unit received at an ownercomputing device configured to communicate data operative tore-transition access to the automated function of the rental unit fromthe traveler access to owner access.
 4. The method of claim 3, whereinowner access to the automated function remains un-blocked until the datarepresenting the emergency at the rental unit is no longer beingreceived at the owner computing device.
 5. The method of claim 1,wherein the data representing the access credentials includes deviceidentification data for a traveler computing device that communicatedthe data representing the access credentials.
 6. The method of claim 1and further comprising: receiving data representing location data for atraveler computing device, the location data indicating the travelercomputing device is positioned within a threshold of an allowabledistance from the rental unit when the data representing the accesscredentials is received.
 7. The method of claim 6, wherein the datarepresenting the location data is determined by data representing anaddress unique to the traveler computing device, data representing aradio frequency signal parameter of the traveler computing device orboth.
 8. The method of claim 1 and further comprising: retaining owneraccess to automated functions of an additional rental unit untiloccurrence of another event; and transitioning access to the automatedfunctions of the additional rental unit from owner access to traveleraccess upon occurrence of the another event.
 9. The method of claim 8,wherein the occurrence of the another event comprises verifying datarepresenting access credentials for the additional rental unit.
 10. Themethod of claim 9, wherein the occurrence of the another event furthercomprises determining data representing a check-in time, a check-in dayor both extracted from the stay data has occurred.
 11. A computingdevice, comprising: a computing resource; a display in communicationwith the computing resource, a data storage resource; and acommunications interface in communication with the computing resourceand the data storage resource, the computing resource configured to:present data representing a service request type for a rental unit onthe display, receive data representing a selection of the servicerequest type, communicate, using the communications interface, datarepresenting the selection of the service request type to a serviceprovider address accessed from the data storage resource, and receivedata representing a service status for the rental unit, and present thedata representing the service status for the rental unit on the display.12. The computing device of claim 11, wherein the service provideraddress comprises an address for a rental owner computing device. 13.The computing device of claim 11, wherein the data representing theservice status comprises one or more of estimated service completiontime, updates on service, notification of a service time range, noticeof completion of service.
 14. The computing device of claim 11, whereinthe data representing the service status is received from a serviceprovider computing device.
 15. A system, comprising: a communicationsinterface; a computing resource; and a data storage resource, thecommunications interface in communication with the computing resourceand the data storage resource, the computing resource configured to:access data representing location data for a location of a travelercomputing device, receive data representing pre-arrival activation dataof an automated function of a rental unit, receive data representing afunction activation time extracted from the pre-arrival activation data,access data representing an estimated time of arrival of the travelercomputing device at the rental unit, calculate an estimated location ofthe traveler computing device at the function activation time, determinea match between the function activation time and a time the travelercomputing device arrives at the estimated location, and activate theautomated function of a match is determined.
 16. The system of claim 15,wherein estimator circuitry in the traveler computing device determinesthe match, the estimator circuitry is coupled with an estimated time ofarrival calculator configured to generate the data representing theestimated time of arrival and a location estimator configured tocalculate the estimated location of the traveler computing device at thefunction activation time.
 17. The system of claim 15, wherein theestimated time of arrival calculator is configured to receive the datarepresenting the location data, to calculate, using the location dataand signals from clock circuitry and motion sensor circuitry of thetraveler computing device, a distance traveled per unit of time, tocalculate, using the location data, a distance from a current locationof the traveler computing device to a location of the rental unit, andto calculate the estimated time of arrival using the distance and thedistance traveled per unit of time.
 18. The system of claim 15, whereinthe automated function that is activated comprises a lighting functionof the rental unit.
 19. The system of claim 15, wherein the automatedfunction that is activated comprises a heating, ventilating, and airconditioning function of the rental unit.
 20. The system of claim 15,wherein the automated function that is activated comprises a securityfunction of the rental unit.